-
-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MNT: update develop branch with changes from master #461
Conversation
- This happens when we use EmptyMotors - ValueError: attempt to get argmax of an empty sequence
BUG: flight.prints.max_values() fails when launching an EmptyMotor
DOC: Add documentation on how to build the docs
Co-authored-by: MateusStano <[email protected]>
Co-authored-by: MateusStano <[email protected]>
Co-authored-by: MateusStano <[email protected]>
This is important because the github actions were not being activated after modifying the .yaml files
- Refined input parameters for apogee and liftoff speed calculations - Inertia definition in the Rocket class - Change the Motor.dry_mass definition - Avoid repetition of dry_mass definitions - Add a few for docstrings
parameter as in Motor class
DOCs: improve mass and inertia docs
I believe #451 could be merged into develop and be released with v1.1.0. I wouldn't call it a major bug that requires a hot fix, since the current behavior is documented. |
That will be released with v1.1.0 anyways, regardless of the head branch, we decided to not have a v1.0.2 version |
@Gui-FernandesBR, I strongly believe we should follow the appropriate protocols here. Since there is no hotfix necessary, all code additions (i.e. not just doc changes) should go directly to develop before master. |
MNT: add codecov integration
ENH: workflows update and new docker files
Pull request type
Checklist
black rocketpy/ tests/
) has passed locallypytest --runslow
) have passed locallyCurrent behavior
I'm opening this PR as a reminder that we need to rebase the develop branch before preparing the release v1.1.0 this week.
New behavior
There are 3 PR waiting on the line to be merged on master. We need to wait for them before merging this PR.
Conflicts may be solved after the 3 PR please.
Breaking change
Additional information
This can only be merged after approved.